Problem Note 58850: Holdout Forecast Accuracy scenarios might fail in a multi-captain environment
 |  |  |  |  |
SAS® Revenue Optimization Holdout Forecast Analysis might fail for some scenarios when running in a grid environment with multiple captains where all captains share access to the data mart via NFS. The MerchIntelGridSvr.log file might contain the following error:
<YYYY-MM-DD HH:MM:SS,MMM> [pool-<n>-thread-<n>] DEBUG - STDOUT: <YYYYMMDD:HH.MM.SS.MM>: FA_OUTPUT: fa_output take <seconds> to finish... <YYYY-MM-DD HH:MM:SS,MMM> [pool-<n>-thread-<n>] DEBUG - STDOUT: <YYYYMMDD:HH.MM.SS.MM>: ERROR: Assertion failed: base_file_exists(this->out_path), file /sas/dev/mva-f4ro52/di/src/output_adapter.c, line 132 <YYYY-MM-DD HH:MM:SS,MMM> [pool-<n>-thread-<n>] DEBUG - STDOUT: <YYYYMMDD:HH.MM.SS.MM>: Error: directory '<di_dm>/FA/<user_id>/<scenario_name>/results' must exist before calling output adapter <YYYY-MM-DD HH:MM:SS,MMM> [pool-<n>-thread-<n>] DEBUG - STDOUT: <YYYYMMDD:HH.MM.SS.MM>: <YYYY-MM-DD HH:MM:SS,MMM> [pool-<n>-thread-<n>] DEBUG - STDOUT: ERROR: TKTException code = 6 (Access violation) <YYYY-MM-DD HH:MM:SS,MMM> [pool-<n>-thread-<n>] DEBUG - STDOUT: #4 0x00002b17cf35c1ac in tkmi_exception_handler (thread=0x7f1f, ctxt=0x2b1859b7be9c, code=TKTE_UnknownException) at /sas/dev/mva-f4ro52/di/src/tkmi_exception.c:88 <YYYY-MM-DD HH:MM:SS,MMM> [pool-<n>-thread-<n>] DEBUG - STDOUT: #5 0x00002b17c5f27116 in bktExcept () from <sashome>/SASFoundation/9.3/sasexe/tkmk.so <YYYY-MM-DD HH:MM:SS,MMM> [pool-<n>-thread-<n>] DEBUG - STDOUT: #6 0x00002b17c5f2a11b in bkt_segv () from <sashome>/SASFoundation/9.3/sasexe/tkmk.so <YYYY-MM-DD HH:MM:SS,MMM> [pool-<n>-thread-<n>] DEBUG - STDOUT: #7 0x00002b17c5f276e4 in bkt_signal_handler () from <sashome>/SASFoundation/9.3/sasexe/tkmk.so <YYYY-MM-DD HH:MM:SS,MMM> [pool-<n>-thread-<n>] DEBUG - STDOUT: #8 <signal handler called> <YYYY-MM-DD HH:MM:SS,MMM> [pool-<n>-thread-<n>] DEBUG - STDOUT: #9 assert_fn (cond=-970847896, cond_str=0x1 <Address 0x1 out of bounds>, file=0x1 <Address 0x1 out of bounds>, line=1, msg=0x18020 <Address 0x18020 out of bounds>) at /sas/dev/mva-f4ro52/di/src/base.c:1648 <YYYY-MM-DD HH:MM:SS,MMM> [pool-<n>-thread-<n>] DEBUG - STDOUT: #10 0x00002b17cf35855d in output_adapter_new3 (params=0x2b17c6220968, abs_path=0x1 <Address 0x1 out of bounds>, subdir=0x1 <Address 0x1 out of bounds>, force_use_schema_from_params=1) at /sas/dev/mva-f4ro52/di/src/output_adapter.c:132 <YYYY-MM-DD HH:MM:SS,MMM> [pool-<n>-thread-<n>] DEBUG - STDOUT: #11 0x00002b17cf35a37d in output_adapter_new2 (para <YYYY-MM-DD HH:MM:SS,MMM> [pool-<n>-thread-<n>] DEBUG - STDOUT: <YYYYMMDD:HH.MM.SS.MM>: ms=0x2b17c6220968, subdir=0x1 lt;Address 0x1 out of bounds>) at /sas/dev/mva-f4ro52/di/src/output_adapter.c:76 <YYYY-MM-DD HH:MM:SS,MMM> [pool-<n>-thread-<n>] DEBUG - STDOUT: #12 0x00002b17cf38c592 in fa_output_run (this=0x2b17c6220968, output_score=1, output_fit_score=1, output_score_for_holdout=1, output_fit=98336, output_fit_detail=327708208, output_holdout=0) at /sas/dev/mva-f4ro52/di/src/fa_output.c:179 <YYYY-MM-DD HH:MM:SS,MMM> [pool-<n>-thread-<n>] DEBUG - STDOUT: #13 0x00002b17cf385d73 in fa_service_output (this=0x2b17c6220968, fa_output=0x1, dim=0x1, mg_est=0x1, fse=0x18020, for_fit=327708208) at /sas/dev/mva-f4ro52/di/src/fa_service.c:842 <YYYY-MM-DD HH:MM:SS,MMM> [pool-<n>-thread-<n>] DEBUG - STDOUT: #14 0x00002b17cf3856f6 in fa_service_process_mg this=0x2b17ec961000, dim=0x2b17f68c6190, mg_est=0x2b18504830f0, fse=0x2b17ec950710) at /sas/dev/mva-f4ro52/di/src/fa_service.c:658 <YYYY-MM-DD HH:MM:SS,MMM> [pool-<n>-thread-<n>] DEBUG - STDOUT: #15 0x00002b17cf3885b2 in fa_service_process_scenario (context=0x2b17eed78b60) at /sas/dev/mva-f4ro52/di/src/fa_service.c:502 <YYYY-MM-DD HH:MM:SS,MMM> [pool-<n>-thread-<n>] DEBUG - STDOUT: #16 0x00002b17cf347f08 in logic_fn (ctxt=0x2b17d4610660, req=0x2b18377be0f0, thread=0x2b1810270630, cb=0x2b17f668bde8) at /sas/dev/mva-f4ro52/di/src/job_manager.c:1281 <YYYY-MM-DD HH:MM:SS,MMM> [pool-<n>-thread-<n>] DEBUG - STDOUT: #17 0x00002b17ce58fd0b <YYYY-MM-DD HH:MM:SS,MMM> [pool-<n>-thread-<n>] DEBUG - STDOUT: 20160812:15.44.20.77: in basicPuddleMain () from <sashome>/SASFoundation/9.3/sasexe/tkepdl.so <YYYY-MM-DD HH:MM:SS,MMM> [pool-<n>-thread-<n>] DEBUG - STDOUT: #18 0x00002b17c5f25926 in sktMain () from <sashome>/SASFoundation/9.3/sasexe/tkmk.so <YYYY-MM-DD HH:MM:SS,MMM> [pool-<n>-thread-<n>] DEBUG - STDOUT: #19 0x00002b17c5f26f7b in bktMain () from <sashome>/SASFoundation/9.3/sasexe/tkmk.so <YYYY-MM-DD HH:MM:SS,MMM> [pool-<n>-thread-<n>] DEBUG - STDOUT: #20 0x0000003570e07aa1 in start_thread () from /lib64/libpthread.so.0 <YYYY-MM-DD HH:MM:SS,MMM> [pool-<n>-thread-<n>] DEBUG - STDOUT: #21 0x0000003570ae893d in clone () from /lib64/libc.so.6 <YYYY-MM-DD HH:MM:SS,MMM> [pool-<n>-thread-<n>] DEBUG - STDOUT: <YYYY-MM-DD HH:MM:SS,MMM> [pool-<n>-thread-<n>] DEBUG - STDOUT: <YYYY-MM-DD HH:MM:SS,MMM> [pool-<n>-thread-<n>] DEBUG - STDOUT: <YYYY-MM-DD HH:MM:SS,MMM> [pool-<n>-thread-<n>] DEBUG - STDOUT: <YYYYMMDD:HH.MM.SS.MM>: Warning: Holdout Failed for Model Group <model_group_id>, Scenario <scenario_name>
This error occurs when Holdout Forecast Accuracy is requested for several model groups in different partitions and those partitions are distributed across multiple captains.
The workaround for this issue is to ensure that all model groups included in a Holdout Forecast Accuracy request reside on the same captain. The simplest way to guarantee that all model groups are on a single captain is to ensure that all model groups in the request are in a single partition.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Markdown Optimization | Microsoft® Windows® for x64 | 5.2_M4 | 5.4 | 9.3 TS1M2 | 9.4 TS1M4 |
| Linux for x64 | 5.2_M4 | 5.4 | 9.3 TS1M2 | 9.4 TS1M4 | ||
| SAS System | SAS Regular Price Optimization | Microsoft® Windows® for x64 | 5.2_M4 | 9.3 TS1M2 | 9.3 TS1M2 | |
| Linux for x64 | 5.2_M4 | 9.3 TS1M2 | 9.3 TS1M2 | |||
| SAS System | SAS Promotion Optimization | Microsoft® Windows® for x64 | 5.2_M4 | 9.3 TS1M2 | 9.3 TS1M2 | |
| Linux for x64 | 5.2_M4 | 9.3 TS1M2 | 9.3 TS1M2 | |||
| SAS System | SAS Retail Forecasting | Microsoft® Windows® for x64 | 5.2_M4 | 9.3 TS1M2 | ||
| Linux for x64 | 5.2_M4 | 9.3 TS1M2 | ||||
A fix for this issue for SAS Revenue Optimization 5.2_M4 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/P20.html#58850A fix for this issue for SAS Size Optimization 3.2_M4 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/P21.html#58850| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2016-10-12 09:56:24 |
| Date Created: | 2016-08-24 10:57:17 |